1 link tagged with all of: ux + seangoedecke + product design
Click any tag below to further narrow down your results
Links
An engineer explains why he loves working with designers but thinks having more than one on a team causes constant conflict, and why design systems, despite being the best option he knows, create friction for engineering teams. He also questions whether many products need designers at all.
- Designers show their value immediately: a placeholder UI gets replaced by a mockup that is better in ways the engineer couldn't have imagined.
- Multiple designers on one project tend to clash because their disagreements rest on taste rather than measurable criteria like latency or bugs, and because users see the product as one design, so every change ripples through.
- Design systems are still the best way the author knows to keep UI consistent, but they create tension between product teams with odd requirements and design teams protecting the look, plus compatibility problems with older frontend code.
- Many teams, like those building APIs or billing systems, don't benefit from designers, and plenty of products succeed despite poor design.